feat: private field for user_metadata table - #21
Merged
Conversation
JerryImMouse
enabled auto-merge (squash)
August 31, 2026 10:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a new
privatefield touser_metadatatable to explicitly say what data is sensitive and which is not.This resulted into a huge changes in the
set_metadataandget_metadataroutes to somehow provide new field :PResolves #10
Why
Some web panels WOULD like to show user's metadata to him, they need a way to determine which is safe to show.
Checklist
cargo fmtpassescargo clippypasses